An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hey, we're stuck in a loop and need help from App Review. App: Latent: Focus Camera (Apple ID 6788947658) Submission: 302fb800-e336-4f51-afef-6bdffdc59320, version 1.0.1 (30) Latent is free. Build 30 has no in-app purchases, no paywall, and no purchase code. We keep getting rejected under 2.1(b) because the reviewer can't find "Latent Pro Yearly" (6813310670) and "Latent Pro Monthly" (6813311816) in the binary. That's correct, they aren't in it. They're leftovers from before we went free. The rejection says to remove them from App Store Connect. We can't: They were never approved. Both show Developer Rejected, with 0 territories, and they aren't part of the submission. There's no Delete button in App Store Connect. DELETE /v1/subscriptions/{id} returns 409 SUBSCRIPTION_DELETE_NOT_ALLOWED. The subscription group can't be deleted while those two are in it. We replied in Resolution Center on Sept 29 and resubmitted. Can someone remove these two subscriptions on your side, or let the reviewer know they aren't part of this version? Thanks, Malcolm

Hello, Our first app submission has been in "Waiting for Review" since September 26, 2026 (5 days now). The submission includes the first app version, our first subscription group with 4 auto-renewable subscriptions, and 3 consumable in-app purchases. We have already contacted App Review through the Contact Us form (Case ID: 102980881885). The demo account in the Review Notes is ready and active. Is there anything we can do from our side to help the review move forward? Thank you.

Submission ID 2b3e5059-d7db-4cff-a15f-29107f090a74 (GreenBet Golf, Apple ID 6761739779) has been In Review since September 11. It contains four items: iOS 1.0.1 build 37, plus two auto-renewable subscriptions and their subscription group in first-time review. The September 11 review raised four issues. All four were resolved the same day and answered in the submission thread, including the screen recording App Review requested for guideline 3.1.2(c). An expedited review was requested and granted on September 23, with no change since. No developer action is pending, the Paid Apps Agreement is active, and there has been no further message from App Review. Could someone take a look at this submission?

I created an app that solved a need for me, after not finding anything like it in the app store. After enrolling multiple testers on testflight, I made several modifications and have very positive response. After submission, this is what happened: Declined because it had "been submitted by a developer account that has a limited App Review history." They wanted a video of me using the app uploaded so they could see the functionality. OK, I recorded the video and gave the information about the value it provides in my reponse. It gets declined next because there's some use of apple terms in the metadata. Fair enough - I missed this, so made the update immediately and resubmitted. Today, it's declined because they felt the app was similar to other apps in the app store after having tested it (?). I'm a bit surprised by this, given there are no other applications available that function the way this is configured. Furthermore, would the same be true if I had submitted a casino game? Slots? Blackjack? Cribbage? I've filed the appeal, but every time adds another 6-10 days of waiting. Is there no way to speak to a human? Is this continual moving of the goalposts the usual for a new developer?

Hi App Review team, • App: Offing — Offline Chat • Apple ID: id6793304688 • Version: 1.1.0 (build 14) • Submission ID: 443edd98-a4e6-4e0e-98ca-794bfb8583c2 On Sept 2 the app received a Guideline 2.1(b) Information Needed request about paid content. I replied that the app is completely free, with no In-App Purchases, subscriptions, accounts, or backend, since it works offline over Bluetooth. I resubmitted the same day. It waited until Sept 19 and has been In Review since then, 11 days as of today. I have a newer build ready but don't want to withdraw this one and restart the queue. Could someone check whether anything else is needed from me? Thank you!

My app was submitted for review on September 9, 2026. It has been stuck in “Waiting for Review” for over 21 days with no progress. I submitted an Expedited Review request (Case: 102962372136), and received confirmation that it was accepted on September 18. However, the status has not changed and no review has started. I have contacted Developer Support multiple times (Sept 14, 18, 22, and 30) and received only identical template responses. They confirmed they cannot provide updates beyond what App Store Connect shows. Given the accepted expedite request and the unusual 21-day delay, I believe this submission may be stuck in an abnormal queue. I am requesting assistance from the App Review team to investigate why this app has not entered review. Apple ID: 6758485727 Version: 3.6.2 App Name: 小趣同学

Hello App Review team, Our submission has been "In Review" since September 19, 2026 (JST). The status hasn't changed and there are no messages in App Store Connect. Submission ID: 292556f9-a3ec-4c70-82aa-4e50aa71c9e9 Submitted: September 18, 2026 / In Review since: September 19, 2026 A separate Product Page Optimization submission for the same app has also been "Waiting for Review" since September 24: Submission ID: be24f6da-d8ad-4eb1-94b0-6832a7b6529c What we have done so far: Requested an expedited review on September 22 Emailed Developer Support. The reply said the review is in progress. Called Developer Support (case 102978078505) and asked them to pass a message to App Review This delay is blocking our release. If anything is needed from us, such as more information or a change to a specific item, please let us know in App Store Connect and we will respond right away. Thank you.

Hello Apple Developer Community, I’m experiencing a serious delay with the App Review process for my app and would appreciate any guidance from Apple or other developers who may have experienced something similar. App: İSGCEP - İş Güvenliği Asistanı Current version: 1.7.0 We have been waiting for the App Review process to be resolved for approximately 25–27 days in total. During this period, previous submissions remained in “In Review” for an unusually long time without receiving a review decision, a message, or a request for additional information. We had also previously requested an expedited review for this app, and Apple confirmed: “We’ll expedite review for İSGCEP - İş Güvenliği Asistanı. If your submission is rejected during this review, you don’t need to request another expedited review when you resubmit. Your resubmission will be automatically returned to the expedited queue.” However, the review did not progress as expected. Because the previous submissions remained stuck for such a long time, I eventually cancelled them and created a new submission for version 1.7.0. The new submission has now been submitted again. I understand that this new submission itself has not been waiting for 25–27 days; rather, the overall review process for this app has been unresolved for approximately 25–27 days due to the previous submissions becoming stuck in “In Review”. There are currently no messages in the Resolution Center and no request for additional information from App Review. Could someone from the App Review team please check whether there is anything unusual with our submission, App Store Connect account, or review queue that could be preventing the app from progressing through review? I’m not asking for approval or a guaranteed review time. I would simply like to make sure that there is no technical or queue-related issue affecting our submission. This delay is particularly concerning because we were previously informed that the app would receive expedited review and that a resubmission would automatically return to the expedited queue. Any guidance from Apple or developers who have experienced a similar situation would be greatly appreciated. Thank you.

I am submitting the app for this competition: https://revenuecat-shipaton-2026.devpost.com/details/dates which has little under 18hrs remaining. The reviewer last night raised an issue which was already resolved in the first review and was answered in the comments. Can someone please assign this review to a different reviewer, preferably someone who reads prior comments and wants to do their job effectively, rather than just dismissing and pushing this out of their queue.

Hi everyone, Our app Aura Balance (Apple ID 6813722719) has been in Waiting for Review since September 25. This is version 3.0.4, a resubmission after a Guideline 4.3(b) rejection. We took the feedback seriously and made real changes: new build, new name, new screenshots and a different primary category. We also replied to the reviewer in App Store Connect and sent an expedited review request. We're a small team and we have a launch event on October 2, so we're a bit nervous. Could someone from App Review check if the submission is still in the queue, or if anything is needed from our side? Thanks a lot.

My Individual Developer account (Team ID: SU8NVE3Z6C) has been suspended due to an automated compliance check regarding digital assets, citing Sections 14.8(a) and 2.8 of the DPLA. I have a clean 13-year track record on the App Store. On September 23, immediately after receiving the automated notice, I submitted all requested documentary evidence directly to provider_review. I provided my official residence documents and description of my apps. They do not involve custody, exchange, trading, or transmission of digital assets, nor do they violate any applicable laws. It has now been over a week since I submitted the full documentation. My entire portfolio of apps remains removed from the App Store. This prolonged downtime is causing severe ongoing financial loss and severely disrupting the experience for my active subscribers. Could an Apple Community Specialist or a senior support engineer please help escalate this review? I have provided everything asked of me and urgently need my account access restored. Thank you in advance for your assistance.

App: Mirra: You in Any Photo (App ID 6806898848), version 1.0. Latest Submission ID: 06677de2-a0fa-489c-8635-65998191f4e6. We have received the same Guideline 1.1 rejection three times, each with identical wording: "Specifically, the app includes templates for generating content showing people making intimate contact with each other, such as hugging, kissing, or other intimate templates." We are asking for help identifying what App Review is referring to, because the app does not contain templates of any kind: There is no template gallery, preset list, sample scene, or bundled content anywhere in the app. The asset catalog contains only the app icon and an accent color. The app has one function: the user supplies a reference photo (from their own library or a link they share) and the app renders that scene with the user's own enrolled face. Our server records show that no images were generated from the review account in any of the three review sessions. The service already declines any reference image showing more than one person, and the next build restricts generation to single-person photos end to end, with the reason shown on screen. Each resubmission included these facts in the review notes and returned the identical paragraph. We have replied in the Resolution Center and requested a call. If anyone from App Review can tell us the specific screen, screenshot, or asset that is being read as a template, we will remove it immediately. Otherwise we would be grateful for a review of the actual build. A demo account with pre-enrolled selfies is in App Review Information. Thank you.

I've been unable to resubmit my app for review for several days, and now App Store Connect can't even load my subscription data. Submission: "Add for Review" / "Resubmit to App Review" on my app version (iOS 1.0) or subscriptions returns "An unexpected error was encountered when submitting for review. If the issue persists please contact us." The app version shows "Removed" and the subscriptions (Monthly, Yearly) show "Developer Rejected," and I can't add them back. Subscriptions page: Distribution → Subscriptions now shows "An error has occurred. Try again later." under both Subscription Groups and Billing Grace Period, so the page can't load my subscription data at all. Diagnostic detail: builds 7 and 9 both fail the submission error (both "Complete" in TestFlight, no Missing Compliance), while an earlier build (5) added for review fine — so submissions work in general; it's specific to the current submission/subscription state. Already tried: fresh incognito + a different browser, removing and re-adding items, uploading new builds, waiting several days. I've emailed Developer Support (no reply yet) and can share the submission ID and app ID with an Apple staffer. Has anyone hit this, or can an Apple staffer help get it unstuck? Thank you.

Hello, My app 岩片 (YanPian, Apple ID 6800534375, bundle ID com.ajin.heartrate) was rejected on September 19, 2026 under Guideline 4.3(a) - Design - Spam. Submission ID: 69a97b70-0219-42fe-861f-ce737bc19b38, version 1.0 (202609061946). The app is original. I wrote it myself, it is the only app on my account, I have not submitted similar apps on any other account, and I have never used or bought an app template. It is a tool for lead climbers who film their climbs from a tripod far below the wall: Heart-rate overlay: pick a climbing video from Photos. Heart-rate samples recorded by Apple Watch are read from HealthKit (read-only), matched to the video by capture time, and drawn on the video with a heart-rate graph. Zoom and follow: the climber is tiny in a wide shot, so the app crops in and follows them with editable keyframes (on-device person detection). Live capture, with an optional Zhiyun CQ5 gimbal that moves only when the climber is about to leave the frame, and an optional Apple Watch companion. Everything runs on device. No account, no backend. What I have done so far: September 20: replied in App Store Connect with the explanation above. No response yet. September 29: submitted an appeal to the App Review Board. An earlier appeal got no confirmation, and I cannot find any record of it. The review was done on an iPad Air. The app is iPhone-only. Without a climbing video in Photos, the home screen only shows "New project" and "Live capture", so I understand it may look like a generic camera app. A screen recording of the full flow is attached to the submission in App Store Connect. If a specific app looks similar, I would be glad to know which part so I can change it. Could someone from App Review take a look? Thank you.

App: Weight Tracker, BMI calculator App Apple ID: 1418885210 Version: 1.6.2 (4), iOS The previous build was rejected under Guideline 2.1 because the ATT prompt was not shown on a fresh install. We fixed it, replied with the requested screen recording, and resubmitted on September 23. The status changed to "In Review" on September 24 and has not changed since. The message thread is locked, so we cannot contact the reviewer. Could someone from App Review check whether the submission is stuck? Thank you.

I submitted my app for a big national event on September 22nd, got a rejection for metadata in two days, and fixed it in the same day. Now the event is in two days, and I'm still in Waiting for Review. I tried to contact support and also submitted an expedited review request yesterday, but still stuck. Is there anything I can do to help speed this up? Or anyone from support who can escalate? We desperately need it live, otherwise it will be too late. Thanks!

Hello, I recently received a Pending Termination Notice for my Apple Developer Program membership. The notice states that my account was identified as having provided false or fraudulent account information, documentation, or representations. I respectfully disagree with this finding. All information and documents I provided to Apple during enrollment and throughout my Developer Program membership are genuine and accurate. I have not intentionally provided false information, fraudulent documentation, or misrepresented my identity. I have complete original supporting documentation available and am fully willing to provide it again to Apple for verification, including identity and other relevant account verification documents. I have already been advised to submit an appeal to the App Review Board within the stated 30-day period, which I intend to do. I would appreciate guidance from anyone who has experienced a similar situation: Is there any additional verification process I should request as part of the appeal? Is there a recommended way to provide supporting identity documents for manual verification? Should I also contact Apple Developer Support in addition to submitting the App Review Board appeal? Is there anything specific that should be included when requesting reconsideration of a Developer Program termination related to Developer Identity? I am fully prepared to cooperate with Apple and provide any documentation necessary to verify the authenticity of my account information. My intention is simply to resolve any misunderstanding or discrepancy and have my Apple Developer Program membership reconsidered after verification. Thank you for any guidance.

Hi, My app Duo Queue has been in "Waiting for Review" since September 22, about 160 hours now, with no status change since then. App: Duo Queue: Game Tracker Apple ID: 6809453548 Version: 1.1 (build 21), submitted with the in-app purchase com.adgames.duoqueue.full_shelf Submission ID: 3ff2dc7d-2435-43a3-bc3f-33b1ae3478d2 Submitted: Sep 22, 2026, 09:05 UTC An earlier submission was rejected under Guideline 4.3(a). For 1.1 I rebuilt the core of the app. Users now photograph a game box and the app identifies it, and game detail pages include trailers where available. I also renamed Swift types that shared names with types in my other apps, and attached a demo video for the reviewer. I withdrew the previous submissions for this app, so this is its only active submission in the queue. I know the team has a lot of apps to get through. I'd just like to confirm that the submission isn't stuck somewhere, or find out if I need to do anything on my side. Thank you.

Hi everyone, I submitted my app for App Review on August 14, 2026, at 2:39 PM. I later submitted an updated version again on September 9, 2026. The latest submission has been showing “In Review” for the past 5 days, but I still haven’t received any review decision or additional information from the App Review team. As I understand it, once an app enters the “In Review” status, a review decision is generally provided after the review is completed. However, in my case, the status has remained unchanged for several days. Has anyone experienced a similar situation recently? Is it normal for an app to remain in “In Review” for this long, or is there anything I should do from my side? Any advice or guidance would be appreciated. Thank you!

Guideline 4.7.2 – Native capabilities for signed B2B HTML5/JavaScript mini apps We are developing a B2B iOS application using .NET MAUI. The application acts as a host for dynamically downloaded HTML5/JavaScript mini apps displayed inside a WebView/HybridWebView. The mini apps are created and distributed exclusively by us. Third parties and end users cannot upload or provide their own mini apps. Each mini app package is digitally signed by us, and the host application verifies its signature and integrity before allowing it to run. The mini apps contain only HTML, CSS and JavaScript and do not contain downloaded native executable code. Some mini apps need access to a very small, predefined set of capabilities implemented by the native host application, for example: Take a photo Scan a QR code or barcode Select a file Potentially print to a supported printer For example, a mini app could call a predefined JavaScript bridge method such as: TakePhoto() The .NET MAUI host application would then present the native iOS camera UI and return the result to that specific mini app. The mini apps would not receive unrestricted access to native iOS APIs. Only an explicitly defined allowlist of host capabilities would be exposed. Access to privacy-sensitive capabilities such as the camera would only occur following an explicit user action, and the normal iOS permission flow would still apply. Would this architecture be acceptable under App Review Guideline 4.7.2? Does the fact that this is a controlled B2B environment, where all mini apps are created, signed, distributed and verified exclusively by us, affect the requirement for prior permission from Apple? If prior permission is still required, what is the correct process for requesting that permission before submitting the application for App Review?